Copy secure_boot flag in boot params across kexec reboot
authorDave Young <dyoung@redhat.com>
Wed, 8 Nov 2017 15:11:32 +0000 (15:11 +0000)
committerBen Hutchings <ben@decadent.org.uk>
Sun, 29 Apr 2018 16:09:14 +0000 (17:09 +0100)
commit411a1ca7a9f7434d56bc7354181a43c11827011d
treef5b8f2b3c2891ca3dbd4988a68df0782f8d7869e
parent26c907cbe778464803225e42c4758e97344fca66
Copy secure_boot flag in boot params across kexec reboot

Kexec reboot in case secure boot being enabled does not keep the secure
boot mode in new kernel, so later one can load unsigned kernel via legacy
kexec_load.  In this state, the system is missing the protections provided
by secure boot.

Adding a patch to fix this by retain the secure_boot flag in original
kernel.

secure_boot flag in boot_params is set in EFI stub, but kexec bypasses the
stub.  Fixing this issue by copying secure_boot flag across kexec reboot.

Signed-off-by: Dave Young <dyoung@redhat.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: "Lee, Chun-Yi" <jlee@suse.com>
cc: kexec@lists.infradead.org

Gbp-Pq: Topic features/all/lockdown
Gbp-Pq: Name 0007-Copy-secure_boot-flag-in-boot-params-across-kexec-re.patch
arch/x86/kernel/kexec-bzimage64.c